Connected payment card systems and methods

ABSTRACT

Methods and systems of managing payment cards are disclosed. A financial institution computing system includes a token database storing a plurality of tokens and token information, a network interface circuit enabling the financial institution computing system to exchange information over a network; and a token management circuit. The token management circuit enables a graphical user interface on a customer device over the network that can be used to generate new token requests, re-provision token requests, and management requests. The management requests enable and disable tokens, such that transactions against a payment card account using an enabled token are completed, and transactions against the payment card account using a disabled token are denied.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/054,633, filed Feb. 26, 2016, which claims the benefit of priority to U.S. Patent Application No. 62/199,783, filed Jul. 31, 2015, both of which are hereby incorporated by reference in their respective entireties.

BACKGROUND

Payment cards can be provided in many forms beyond a plastic card with a magstripe. Payment cards can be provided with on-board integrated circuits and can be provisioned to mobile devices for mobile wallet transactions. Such arrangements can be used for both in-person and on-line transactions. However, while payment cards reduce the need to carry physical currency, payment card transactions can entail security risks. Further, many existing systems manage security issues on an account-by-account basis. As such, a customer may have to freeze or close an entire payment card account as a result of a security breach at a single merchant. Resorting to an account-wide freeze can be significantly disruptive, particularly where the customer has a limited number of available payment source accounts.

SUMMARY

One example embodiment relates to a financial institution computing system. The system includes a token database, a network interface circuit, and a token management circuit. The token database retrievably stores a plurality of tokens and token information associated with each of the plurality of tokens. The network interface circuit enables the financial institution computing system to exchange information over a network. The token management circuit is configured to enable a graphical user interface on a customer device over the network. The token management circuit is further configured to cause a new token to be provisioned in response to a new token command generated by the graphical user interface. The token management circuit is configured to cause a token to be re-provisioned in response to a re-provision token command generated by the graphical user interface. The token management circuit is further configured to enable and disable tokens in the token database in response to management commands generated by the graphical user interface. Transactions against a customer payment card account using an enabled token are completed, and transactions against the customer payment card account using a disabled token are denied.

Another example embodiment relates to a method of enabling real time payment card account management for customers of a financial institution, including management of physical payment cards, as performed by one or more circuits at a financial institution computing system. The method includes retrievably storing, by a token database, a plurality of tokens and token information associated with each of the plurality of tokens. The method further includes enabling, by a network interface circuit, the financial institution computing system to exchange information over a network. The method includes enabling, by a token management circuit, a graphical user interface on a customer device over the network. The method further includes responding, by the token management circuit, to requests provided by the graphical user interface, including causing a new token to be provisioned in response to a new token request, causing a token to be re-provisioned in response to a re-provision token request, and enabling and disabling tokens in the token database in response to management requests. A transaction against a customer payment card account using an enabled token is completed, and wherein a transaction against the customer payment card account using a disabled token is denied.

Yet another arrangement relates to a non-transitory computer readable media having computer-executable instructions embodied therein that, when executed by a processor of a financial institution computing system, cause the financial institution computing system to perform operations to enable real time payment card account management for customers of a financial institution, including management of physical payment cards. The operations include retrievably storing, by a token database, a plurality of tokens and token information associated with each of the plurality of tokens. The operations further include enabling, by a network interface circuit, the financial institution computing system to exchange information over a network. The operations include enabling, by a token management circuit, a graphical user interface on a customer device over the network. The operations further include responding, by the token management circuit, to requests provided by the graphical user interface, including causing a new token to be provisioned in response to a new token request, causing a token to be re-provisioned in response to a re-provision token request, and enabling and disabling tokens in the token database in response to management requests. A transaction against a customer payment card account using an enabled token is completed, and wherein a transaction against the customer payment card account using a disabled token is denied.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a payment card and token provisioning system, according to an example embodiment.

FIG. 2 is a block diagram illustrating additional features of the payment card and token provisioning system shown in FIG. 1.

FIGS. 3A-3D are depictions of various screens generated on a user interface, which may be used to facilitate a payment transaction, according to example embodiments.

FIG. 4 is a flowchart of a method of provisioning a payment card, according to an example embodiment.

DETAILED DESCRIPTION

Referring to FIG. 1, a payment processing system 100 includes a financial institution computing system 102, a customer device 104, a merchant computing system 106, and a card network computing system 108. A network 110 enables components of the system 100 to communicate with each other. The network 110 is a data exchange medium, which may include wireless networks (e.g., cellular networks, Bluetooth®, WiFi, Zigbee®, etc.), wired networks (e.g., Ethernet, DSL, cable, fiber-based, etc.), or a combination thereof. In some arrangements, the network 110 includes the internet.

In example embodiments, payment processing system 100 uses payment tokens to facilitate payments to merchants. In example embodiments, payment tokens may be surrogate values that replace the primary account number (PAN) associated with a payment card, such as a credit card, debit card, stored value card, etc. Payment tokens may pass basic validation rules of an account number. Hence, the payment token for a credit card in many respects “looks like” a real credit card number, but in fact is only a token. As part of the token generation process, steps are taken such that the generated payment token does not have the same value as or conflict with a real primary account number (e.g., a real credit card number). Payment tokens may be provisioned to various locations for use in various types of payment scenarios, including remote storage at a merchant (e.g., a card-on-file database) for on-line transactions with the merchant, a secure storage element (“secure element”) located in a payment card for a point-of-sale transaction using the payment card, local device storage (e.g., internal memory of a mobile device) for a mobile/digital wallet transaction, and so on.

In example embodiments, to process payment transactions, a payment is processed using a payment token in lieu of a primary account number (e.g., the 16-digit account number on the front of a credit card). The merchant obtains the payment token from a customer device or from the payment card, and then submits the payment token through a payment network to a computing system associated with a card network (e.g., Visa®, MasterCard®, American Express®, Discover®, Diners Club®, etc.). The card network computing system detokenizes the payment token to obtain the PAN, i.e., replaces the payment token for its associated PAN value based on the payment token-to-PAN mapping information stored in a token database (sometimes referred as a “token vault”). The card network computing system then transmits the PAN to the card issuer (e.g., the customer's financial institution) for processing in a manner similar to a traditional credit card transaction. For example, the card issuer may approve the transaction, in which case the transaction with the merchant is completed and payment to the merchant is made. The token database may also maintain other information that may be used to apply restrictions or other controls during transaction processing.

In example embodiments, processing payment transactions using such payment tokens provides enhanced security in connection with the payment card transactions. The payment tokens may be limited to use, e.g., only in connection with a specific merchant or a specific channel (e.g., payment via a specific mobile wallet). For example, in the event of a data breach at a merchant, the risk of subsequent fraud is reduced because only the payment tokens are exposed instead of primary account numbers. In this example, the payment tokens are merchant-specific and therefore cannot be used at other merchants. Although the examples provided herein relate primarily to the use of payment tokens (which may be used to originate payment transactions), the systems and methods described herein may also be used with and non-payment tokens (which may be used for ancillary processes, such as loyalty tracking), as described in greater detail below.

Referring again in detail to FIG. 1, the financial institution computing system 102 is a computing system at a financial institution that is capable of maintaining customer accounts (e.g., payment card accounts, such as credit card accounts, demand deposit accounts having an associated debit card, stored value card accounts, and so on) and databases of customer information. In the context of the present disclosure, the financial institution can include commercial or private banks, credit unions, investment brokerages, and so on.

The customer device 104 is a computing system associated with a customer of the financial institution. The customer device 104 includes one or more processors and non-transitory storage mediums housing one or more logics configured to allow the customer device 104 to exchange data over the network 110, execute software applications, access websites, generate graphical user interfaces, and perform other operations. Examples of the customer device 104 include laptop computers, desktop computers, mobile devices (tablets, smartphones, wearable computing devices such as eyewear, etc.), and so on.

The merchant computing system 106 is a computing system associated with a merchant with which a customer of the financial institution may transact. Examples of merchants include, for example, retailers, wholesalers, marketplace operators, service providers (e.g., loan servicers, cleaning services, transportation providers, digital wallet services, and so on), and so on. In some arrangements, the merchant computing system 106 is used to create and store data relating to customer transactions (e.g., purchases and refunds). In some such arrangements, the merchant computing system 106 can store databases of information relating to customers such as names, shipping addresses, contact information, and so on. Further, the merchant computing system 106 may be able to operate customer loyalty programs (e.g., membership programs, points programs, frequent shopper discounts, and so on).

The card network computing system 108 is a computing system associated with a card network. Examples of card networks include Visa®, MasterCard®, American Express®, Discover®, Diners Club®, etc. In some embodiments, the card network computing system 108 generates tokens for payment cards. The card network computing system 108 performs operations associated with the generation and issuance of payment tokens. The card network computing system 108 also maintains the established mapping of payment tokens-to-PANs in a token database (or token vault). The card network computing system 108 also detokenizes payment tokens during processing of payment transactions to determine actual account numbers.

Referring now to FIG. 2, system 100 is shown in greater detail according to one example embodiment. In FIG. 2, the financial institution computing system 102 includes a FI customer database 202, a token database 204, a token management circuit 206, a data exchange circuit 208, and an FI network interface circuit 210. The FI network interface circuit 210 is configured to allow the financial institution computing system 102 and the various components therein to exchange data over the network 110.

The FI customer database 202 allows the financial institution computing system 102 to retrievably store customer information relating to the various operations discussed herein, and may include non-transient data storage mediums (e.g., hard drives, local network servers, and the like) or remote data storage facilities (e.g., cloud servers). The FI customer database 202 includes personal customer information (e.g., names, addresses, phone numbers, and so on), identification information (e.g., social security numbers, driver's license numbers, biometric data, and so on), customer financial information (e.g., account numbers, account balances, available credit, credit history, transaction histories, etc.), and so on.

The token database 204 is a storage medium which may be similar to the FI customer database 202, except that the token database 204 stores token information. The token database 204 may be a token vault that is maintained by the FI computing system 102. Hence, in some embodiments, the payment tokens are generated by the card network computing system 108, and payment token-to-PAN mapping information is maintained by the card network computing system 108; and, in addition, the payment token-to-PAN mapping information is also maintained by the FI computing system 102. For example, in some embodiments, the FI computing system 102 may provide additional token-related management services to customers that are not available through the card network computing system 108. Such services may be useful in situations where customers have multiple different types of accounts, e.g., multiple different types of credit cards, such that a single card network computing system does not have a global view of all of the payment tokens in existence for a given customer. Such services may also be useful in situations in which information in addition to account numbers is tokenized by FI computing system 102 (or other computing systems), thereby creating tokens that are not payment tokens.

To this end, in some embodiments, the token management circuit 206 is configured to enable such services. The services may be provided both in connection with non-payment tokens and in connection with payment tokens. Regarding non-payment tokens, in one aspect, the token management circuit 206 can generate a new unique code to be provisioned as a token, and associate a discrete piece of data with the new unique code (e.g., information other than a payment card number). The new unique code then becomes a token, which may be exchanged among computing devices.

In another aspect, with regard to payment tokens, the token management circuit 206 may be configured to cooperate with card network computing system 108 to activate and deactivate individual payment tokens. In other words, the token management circuit 206 may be configured to provide token-related management services to customers to activate and deactivate individual payment tokens or to otherwise configure permissions associated with such tokens. For example, a customer opening a new credit card account may be assigned a primary account number (PAN) specifically identifying that new account (e.g., a sixteen-digit credit card account number) by the FI computing system 102 and/or by the card network computing system 108. The customer may engage in transactions with one or more merchants, each of which may be assigned a payment token specific to each merchant or to a specific payment channel (e.g., a specific brand of mobile wallet). The card network computing system 108 may generate each of the payment tokens and provide information about the payment tokens to the FI computing system 102. The token management circuit 206 may be configured to cooperate with card network computing system 108 to maintain the payment tokens over their lifecycle in the databases 204 and 228.

In some embodiments, the token management circuit 206 provides a token management hub tool accessible via the customer device 104. The token management hub may be provided as a graphical user interface and presented to a customer via the customer device 104. The customer can access the management hub through via an online banking website, via a mobile banking tool provided to a mobile device, and/or in another manner. The customer may be required to provide login credentials (e.g., username and password, biometrics, etc.). Upon authenticating the customer, the data exchange circuit 208 may transmit account information for that customer from the FI customer database 202 and/or the token database 204 to the customer device 104 to provide the token management hub.

The management hub provides the customer with information relating to tokens provisioned by the card network computing system 108 and/or the FI computing system 102 and related permissions, and allows the customer to manage the tokens. The management hub may also allow the customer to monitor payment tokens issued for a given payment account. For example, the management hub may serve as an interface between the financial institution computing system 102 and the customer, wherein the customer can selectively allow and disallow transactions involving specific payment card accounts with individual merchants, service providers, and digital wallet services. In some arrangements, allowing and disallowing transactions can be performed by activating and deactivating individual payment tokens. Further, PANs may be activated or deactivated at the management hub to selectively enable and disable all transactions involving a particular payment card account. In addition, in some arrangements, the management hub can provide the customer with an alert that a payment token has been reprovisioned when a given payment token is compromised (e.g., in the event of a security breach at a corresponding merchant computing system 106, or a new PAN where a physical credit card is lost).

For example, after a customer opens a new payment card account, the customer may subsequently lose the payment card associated with the card account. However, the customer may be unsure whether the payment card has simply been temporarily misplaced, or whether the payment card has been permanently lost. The customer may be provided with the ability to access the token management hub to temporarily deactivate the payment card for use with all merchants. Subsequently, the customer may locate the payment card, and utilize the token management circuit to reactivate the payment card. Alternatively, the customer may decide that the payment card is permanently lost, and the token management circuit 206 may interact with the card network computing system 108 to deactivate the payment card and cause a new payment card to be issued. Once the new payment card is created, the card network computing system 108 may operate to generate new payment tokens to replace the payment tokens associated with the old payment card, and circulate the new payment tokens to the respective merchants associated with the old payment tokens.

As another example, the management hub may also allow the customer to monitor payment tokens issued for a given payment account. For example, the management hub can provide a list of all merchants having a payment token corresponding to a given payment card account. As such, the customer may be able to see whether any new or unusual payment tokens have been provided without the permission of the customer (e.g., where a fraudster in possession of the payment card attempts to transact with a new merchant). A new or unusual payment token appearing in the management hub circuit 212 may indicate that the payment card has been compromised. For example, a fraudster may obtain a user's credit card information, and use that credit card information in an online transaction, thereby triggering the creation of a fraudulent payment token at the online merchant. The customer may subsequently realize that the payment card has been compromised and may have the payment card deactivated. However, the customer may also recognize the existence of the unusual/fraudulently-created payment token at the unknown merchant prior to the deactivation. The customer may then deactivate that specific payment token for that merchant, thereby causing the financial institution computing system 102 to deny any future transactions for the payment card involving that merchant using the fraudulently-created payment token.

Additionally, the customer may choose to allow or disallow future transactions with a given merchant by updating permissions associated with a corresponding payment token. For example, a customer may visit a merchant once (e.g., while on vacation, while purchasing a gift for a relative, etc.). Such a merchant may be a merchant that the customer is unlikely to visit again. Hence, the customer may decide to deactivate the payment token for that merchant, since the customer is unlikely to visit that merchant again. As another example, the customer may have purchased an item from a service that provides automatic renewals, such that the customer is charged on a periodic basis (e.g., the customer is charged a $24.99 monthly service fee unless the customer takes steps to prevent the fee). In such a situation, the customer may deactivate the payment token for that merchant to prevent such unwanted recurring fees from being charged in the future.

As another example, the management hub may permit the customer to sort tokens according to various parameters, such as by merchant category, most recent transaction date, transaction amount and so on. For example, the customer may be provided with the ability to sort merchant-specific payment tokens by merchant classification code. In this manner, the customer may identify payment tokens associated with merchants that do not fit into the categories of merchants from which the user normally purchases goods/services, which may suggest that those tokens were fraudulently created. On this basis, the user may decide to deactivate such tokens or the entire payment card. Likewise, the customer may sort payment tokens by most recent transaction date and decide, e.g., to deactivate any payment token that has not been used in the past year.

As another example, the management hub can be used to provide information to customers about token activity. For example, if there is a data breach at a particular merchant, the card network computing system 108 may deactivate the payment token for that merchant and reprovision a new payment token for use with that merchant. The management hub can provide the customer with an alert that a payment token has been reprovisioned responsive to the data breach.

The data exchange circuit 208 of the FI computing system 102 is configured to exchange data among the FI customer database 202, the token database 204, the merchant computing system 106, and the customer device 104. In one aspect, the data exchange circuit 208 may be configured to exchange tokens and permissions with the token database 204 and external computing systems (e.g., the merchant computing system 106 and the customer device 104). For example, the data exchange circuit 208 may provide a new token received from the card network computing system 108 to a customer device 104.

The customer device 104 includes customer network interface circuit 212 and customer I/O devices 214. The customer network interface circuit 212 is configured to allow the customer device 104 to exchange data over the network 110. The customer I/O 214 includes hardware and associated logics configured to enable a customer to exchange information with the customer device 104. An input aspect of the customer I/O 214 allows the customer to provide information to the customer device 104, and can include, for example, a mechanical keyboard, a touchscreen, a microphone, a camera, a fingerprint scanner, a user input device engageable to the customer device 104 (e.g., via a USB, mini USB, or micro USB port, etc.), and so on. In turn, an output aspect of the customer I/O 214 allows the customer to receive information from the customer device 104, and can include, for example, a digital display, a speaker, LEDs, and so on.

In some situations, the customer device 104 may receive and display screens including account information, transaction instructions, and so on. In one embodiment, a screen may be used to request a username and password information from the user, to prompt the user to provide information regarding the amount of a payment and which merchant or individual (e.g., name, address, phone number or e-mail, a selection of a recipient by the user from his/her memory or from the customer device 104, etc.) is to receive the payment. Such screens are presented to the user via the display device portion of the customer I/O 214. An input device portion of the customer I/O 214 may be used to permit the user to initiate account access and to facilitate receiving requested information from the user.

In some situations, the customer device 104 may be a mobile device, such as a cellular phone, smart phone, mobile handheld wireless e-mail device, wearable device, portable gaming device, or other suitable device. In some embodiments, the mobile device may include a mobile wallet client application 216. The mobile wallet client application 216 or mobile wallet circuit may include program logic executable by mobile device 104 to implement at least some of the functions described herein. In order to make the mobile wallet circuit 216, the FI computing system 102 may provide a software application and make the software application available to be placed on the mobile device 104. For example, the FI computing system 102 may make the software application available to be downloaded (e.g., via the online banking website of the mobile wallet bank, via an app store, or in another manner). Responsive to a user selection of an appropriate link, the mobile wallet application may be transmitted to the mobile device and may cause itself to be installed on the mobile device 104. Installation of the software application creates the mobile wallet circuit on the mobile device 104. Specifically, after installation, the thus-modified mobile device 104 includes the mobile wallet circuit (embodied as a processor and instructions stored in non-transitory memory that are executed by the processor).

In some situations, payment is made using a payment card 218. The payment card 218 is a physical payment card associated with a payment card account (e.g., a credit card account, a checking account, a prepaid account, etc.) for a given customer, and is capable of exchanging information stored in memory in the payment card 218. The payment card 218 can also include visible information on the face of the card.

The payment card 218 includes a chip 219, a magstripe 220, and a PAN indicator field 221. The PAN indicator field 221 conveys an account number corresponding to a customer payment card account, and may be printed or embossed on the physical payment card 218 (e.g., along with a customer name, expiration date, security codes, etc.). The magstripe 220 is a magnetically-responsive strip disposed on the face of the payment card 218. The magstripe 220 is configured to store a limited amount of information (e.g., a payment card account number, a customer name, expiration date, etc.), e.g., in Track 1/Track 2 format. The chip 219 is a defining feature of the “smart” aspect of the payment card 218. The chip 219 is a small circuitry system configured to exchange data via electrical contacts, RFID communication, NFC communication, or in another manner. The chip 219 can be configured to be able to selectively transmit various types of information, including payment card information (e.g., account numbers, issuing entities, and so on), identifying customer information (e.g., customer name, billing address, phone number, and so on).

In some arrangements, in addition to the PAN which is displayed in PAN indicator field 221, the payment card 218 is further provided with channel-specific payment tokens in the chip 219 and the magstripe 220. The PAN displayed in indicator field 221, the channel-specific token stored in the chip 219, and the channel-specific token stored in the magstripe 220 may each be different numbers. Hence, rather than being programmed with the PAN, the chip 219 and the magstripe 220 are programmed with channel-specific payment tokens which are each different than the PAN. Accordingly, if a transaction involves the customer entering payment card information into an online interface (e.g., a checkout section of an online merchant), then the transaction is completed using the PAN of the payment card as presented in indicator field 221. Specifically, the merchant may transmit the PAN to the card network computing system 108 via the payment network, and the card network computing system 108 may return a payment token to the merchant computing system 106 to store in database 222 for future card-on file transactions. Likewise, if a transaction involves the customer swiping the payment card at a point of sale, then the transaction is completed using the payment token stored in the magstripe 220. Likewise, if a transaction involves the customer inserting the payment card into a chip reader at a point of sale, then the transaction is completed using the payment token stored in the chip 219. As such, the FI computing system 102 may be able to distinguish customer transactions completed via the PAN displayed on the front of the card (e.g., where a payment card account number is provided to an online merchant), the magstripe 220 (e.g., at a magstripe reader at a merchant point of sale), or the use of the chip 219 (e.g., at a chip reader at a merchant point of sale).

In some arrangements, the chip 219 stores customer information in addition to payment card account information. For example, customer identification information may be stored at the chip 219 (e.g., a name and address of the customer, driver's license number, a customer portrait image, etc.). In some embodiments, rather than storing the identification information itself, a token is stored that may be exchanged for the identification information. As such, the chip 219 may be used by a merchant computing device 106 for personal identification of the customer (e.g., to pick up airline tickets at an automated kiosk). For example, the merchant computing system 106 may read the identification information directly from the chip 219, or may submit the token to the FI computing system 102, depending on where the identification information is stored.

In some embodiments, e.g., in situations where a token is stored rather than the identification information itself, the customer may access token management circuit 206 in order to update the information associated with the token. Hence, each time a transaction occurs, the merchant computing system 106 may submit the token to the FI computing system 102 in order to verify that the address information stored by the merchant computing system 106 for the customer is the most recent/up-to-date information.

In some embodiments, the information that is stored (either locally on the chip 219 or remotely accessible via a token) may include information for the merchant to establish a loyalty account. Hence, rather than ask the customer to fill out a form to provide information to establish a loyalty account, the merchant computing system 106 may instead read the information used to create the loyalty account from the payment card 218.

In some embodiments, merchant or financial institution loyalty programs may be implemented with loyalty account numbers that are specific to each customer, and the loyalty account numbers (or tokens representing the loyalty account numbers) may be stored on the chip 219. As such, the loyalty account numbers may be retrieved from a chip reader (e.g., at every transaction involving the payment card 218), e.g., thereby avoiding the need for the customer to separately present a loyalty card or a phone number associated with the loyalty account at the point of sale. In other embodiments, each customer may be assigned a unique ID that is universal across multiple loyalty programs. Hence, the merchant computing system 106 may be configured to identify the customer based on the unique ID, and then provide loyalty program rewards to the customer using the unique ID as the basis for identifying the customer.

As another example, in some embodiments, the chip 219 may be read/writable by the merchant computing system 106 (e.g., the merchant point-of sale-device can read from and write to the chip 219). In such embodiments, rewards balance information may be stored directly on the payment card 218, and used as currency in future transactions with the merchant.

The merchant computing system 106 includes a merchant customer database 222 and a merchant network interface circuit 224. The merchant network interface circuit 224 is configured to allow the merchant computing system 106 to exchange data over the network 110. The merchant customer database 222 is a local or remote data storage system, and may be configured to store customer information relevant for completing purchase transactions. For example, the merchant customer database 222 can include customer names, shipping addresses, billing addresses, payment card information (e.g., tokens), phone numbers, and so on.

The card network computing system 108 comprises a token management circuit 226 and a token database 228. The token management circuit 226 is configured to generate and manage tokens associated with payment cards. The token database 228 maintains the mapping of payment tokens-to-PANs, such that payment tokens may be detokenized during processing of payment transactions to determine actual account numbers. The card network computing system 108 also includes a network interface circuit 230 which is configured to allow the card network computing system 108 to exchange data over the network 110.

Referring now to FIGS. 3A-3D, as previously indicated, the customer may use the customer device 104 to manage payment tokens via the token management circuit 206. For example, the customer may enable and disable financial transactions with individual merchants (e.g., merchants associated with the merchant computing system 106) against one or more payment cards. Further, in some arrangements, the customer may also be able to selectively enable and disable exchanges of customer data (e.g., customer names, shipping addresses, contact information, and the like), by type of customer data and/or by individual merchants. The customer device 104 may also be used to secure a payment card account in the event that the payment card account is compromised at a specific merchant, or the new payment card account itself is compromised. Such an arrangement is shown in greater detail in FIGS. 3A-3D.

Referring first in detail to FIG. 3A, an example graphical user interface (“GUI”) 300 is provided on a user device 104 (e.g., via the customer I/O 214). The GUI 300 is generated by the token management circuit 206. In one arrangement, the GUI 300 presents a customer with a welcome page 310 after the user provides authorizing credentials (e.g., a username and password, an entry of biometric data, or the like via the customer I/O 214). The welcome page 310 includes a plurality of menu buttons 304, each of the menu buttons 304 being labeled with a corresponding action that the token management circuit 206 may perform (e.g., see account information, send payments, etc.). Included among the menu buttons 304 is a labeled button corresponding to the management hub.

Referring now to FIG. 3B, in response to a user selection of the management hub option within the menu buttons 304 provided in FIG. 3A, the GUI 300 has refreshed to show a management hub page 320. Information provided on the management hub page 320 includes information from the token database 204, which may be accessed and transmitted by the data exchange circuit 208 over the network 110 via the FI network interface circuit 210. In one arrangement, the management hub page 320 is organized into a first payment card account section 321 and a second payment card account section 322. Each payment card account section corresponds to a payment card account provided by the financial institution associated with the financial institution computing system 102. As shown in FIG. 3B, two payment card account sections are provided, indicating that the user is associated with two payment card accounts.

A sample window 323 (i.e., highlighted for illustrative purposes) of a portion of the first payment card account section 321 is provided to indicate various types of information provided in a given payment card account section. The sample window 323 includes a payment card account identifier 324 (e.g., identifying a credit card with a PAN ending in “-0123”). In one arrangement, a user can select a PAN reprovisioning button 325, thereby causing the management circuit 206 to initiate issuance of a new payment card with a new PAN to the customer. (As will be appreciated, although certain terminology is used in the user interface example of FIGS. 3A-3D, other terminology may also be used in practice.) The token management circuit 206 may then cooperate with the card network computing system 108 to generate a new PAN for a new payment card, generate new payment tokens for the new payment card, distribute those payment tokens to merchants and other channels, and update the token databases 204 and 228.

The sample window 323 also includes a merchant identifier 326. The merchant identifier 326 specifies a merchant to which a payment token has been assigned. Using a pair of enabling toggles 327, a user may adjust the payment token permissions stored at the token database 204 for each merchant associated with a given payment card account. Upon choosing to disable a given payment token via the corresponding enabling toggle 327, the token management circuit 206 disallows any additional transactions for the merchant corresponding to the merchant identifier 326 involving the payment card account associated with the payment card account identifier 324. Disabling the payment token may involve updating corresponding data in the token database 204. In turn, choosing to enable the payment token will cause the token management circuit 206 to allow such transactions.

In addition, if a user no longer wishes to transact with a given merchant, or if a payment token was created accidentally or fraudulently, the user may select a payment token deletion button 329 to remove a corresponding payment token from the token database 204 altogether.

Referring now to FIG. 3C, in some arrangements, the GUI 300 can provide an account page 330 specific to a given payment card account. The account page 330 can include a single payment card account section 331 having information and functionalities similar to that offered by payment card account sections (e.g., the first payment card account section 321 and the second payment card account section 322) in the account security hub page 320 (e.g., token management functions).

In some arrangements, the account page 330 includes a representative card image 332. The card image 332 may represent the appearance of a physical payment card corresponding to a given payment card account. For example, where a customer was provided a physical payment card bearing a customized image on a front side of the card (e.g., a favorite picture such as a picture of a family member(s), a pet, a landscape, etc.), the card image 332 may include the customized image as well. The card image 332 may be stored in the FI customer database 202, and provided to the customer device 104 over the network 110 after the customer hub circuit 212 is set up (e.g., via the data exchange circuit 208 in cooperation with the FI network interface circuit 210).

In some embodiments, the card image (e.g., as presented via mobile wallet circuit 216) can change at a point of sale to reflect characteristics of the point of sale transaction. For example, if the customer is at a pet store, the card image may change to show a picture of the customer's pet. Conversely, if the customer is at a floral shop, the card image may change to show a picture of the customer's spouse/significant other. The mobile wallet circuit 216 may be configured to determine point of sale characteristics via, for example, a GPS functionality at the customer device 104, or access to a local wireless network associated with a given merchant.

The card image 332 may also include a notification 333. In some arrangements, the notification 333 is incorporated into the card image 332 (e.g., as a symbol as shown, as an indicative color of a corresponding color code, or the like). The notification 333 can provide notice to a user of some status or condition relating to the payment card account corresponding to the account page 330. For example, information in the FI customer database 202 may show that a card payment is coming due, that a certain amount of a balance or credit limit or budget has been expended, or some other aspect may need attention. Such information may be reflected in the notification 333 as a color (e.g., red for approaching or exceeding spending limits), a symbol (e.g., an exclamation mark for an upcoming due date), or the like. In some arrangements, the notification 333 is a selectable button, wherein the GUI 300 refreshes to provide the user with an appropriate screen (e.g., a payments screen, a transaction history screen, etc.).

Referring now to FIG. 3D, the GUI 300 may provide a customer information page 340 (e.g., responsive to a user selection of a menu button 304 on the welcome page 310 corresponding to customer information). In some arrangements, the customer information page 340 includes an information listing 341 corresponding to personal and identifying information in textual form. For example, the information listing 341 may include a name, address, phone number, and email address. Other similar types of information may be included in the information listing 341 as well. Further, in some arrangements, the customer information page 340 may reflect successful collection of customer biometric data. For example, a stored fingerprint 342 and iris scan 343 specific to the user may be included or acknowledged in the customer information page 340. Such information may then, for example, also be propagated to other user devices, such that the user can use the same biometrics to access other devices.

In some arrangements, a user may be able to select an update button 344 in order to update or revise the information in the customer information page 340. Information in the customer information page 340 may be stored in the FI customer database 202 at the financial institution computing system 102, and exchanged with the customer device 104 and the merchant computing system 106 via the data exchange circuit 208 (e.g., over the network 110 by the FI network interface 210). Further, some or all of the information in the customer information page 340 may be stored in the chip 219 of the issued payment card 218. Upon selecting the update button 344, updated or revised information can be received by the customer device 104 (e.g., via an appropriate aspect of the customer I/O 214), and then transmitted to the data exchange circuit 208 over the network 110. The data exchange circuit 208 may store the updated or revised information in the FI customer database 202 as well as circulate it to the merchant computing system 106. The data exchange circuit 208 may also cause the chip 219 to be updated, for example during a data exchange with the financial institution computing system 102 at a point of sale or a brick and mortar banking location, or by issuing a new payment card 218 with an updated chip 219.

As such, the GUI 300 can be configured to provide a way for the customer to update information at the FI customer database 202. For example, after a customer moves to a new residence, the customer may access the customer information page 340 on the customer device 104, select the update button 344, and enter an updated mailing address into the customer device 104. The customer device 104 subsequently transmits the updated mailing address to the financial institution computing system 102 over the network 110, where it is received by the data exchange circuit 208. The data exchange circuit 208 may store the updated mailing address in the FI customer database 202.

In some arrangements, the data exchange circuit 208 may also provide the updated mailing address to one or more merchant computing systems 106. In one such arrangement, the data exchange circuit 208 accesses the token database 204 to identify merchants corresponding to customer-enabled payment tokens (e.g., via the enabling toggles 327). Upon identifying such merchants, the data exchange circuit 208 may transmit the updated mailing address to their respective merchant computing systems 106 over the network 110 via the FI network interface circuit 210.

In another such arrangement, the data exchange circuit 208 accesses the FI customer database 202 to identify merchants corresponding to previous payment transactions. For example, the data exchange circuit 208 may be configured to search through transaction histories of a customer in the FI customer database 202 to identify such merchants. In some arrangements, the data exchange circuit 208 may be configured to limit the search to transactions within a specific timeframe (e.g., within the past year, within the past six months, etc.). Further, the data exchange circuit 208 may be configured to also confirm that any merchants identified in the transaction histories correspond to customer-enabled tokens in the manner discussed above.

The data exchange circuit 208 may transmit the updated mailing address to a merchant computing system 106 upon receiving and processing the updated mailing address on a rolling basis or in batches. Alternatively, the data exchange circuit 208 may provide the updated mailing address to a merchant computing system 106 upon receiving a transaction request from the merchant computing system 106. In effect, the next time the customer orders from one of the customer-enabled merchants, the customer may not need to provide the updated mailing address to complete the transaction. Other types of customer information (e.g., phone numbers, email addresses, identification information, loyalty program information, etc.) may be updated in a similar manner.

In addition, in some arrangements, token management circuit 206 is configured to provide some or all aspects of the GUI 300 on multiple channels, enabling the GUI 300 to be viewed and manipulated by multiple users. For example, a financial institution I/O (e.g., similar to the customer I/O 214, but disposed at a financial institution facility) may be configured to allow a customer service representative to interface with the financial institution computing system 102. The token management circuit 206 may be configured to provide the GUI 300 at both the financial institution I/O and the customer I/O 214 simultaneously (e.g., over the network 110 via the FI network interface circuit 210). As such, the customer service representative may be able to guide a customer through GUI 300 in real time. In addition, both the customer service representative and the customer may perform any of the operations discussed above while simultaneously viewing the same pages of the GUI 300.

FIG. 4 illustrates a process 400 that may be implemented by the system of FIGS. 1-2. By way of example, FIG. 4 shows a mobile wallet transaction. As will be appreciated, the system 100 supports other types of transactions as well, such as card on file transactions, card present transactions, and so on.

When a user wishes to make a payment at a merchant, for example, the user may access the mobile wallet client application 216 by entering a PIN or other login credentials and then selecting a “pay now” or similar button. For example, the user may be located at a merchant location and may wish to pay for a good or service. As another example, the user may be located away from the merchant location or be engaged in an online transaction.

At step 401, the mobile device 104 may transmit a payment token to merchant computer system 140 (e.g., using a QR code, NFC, wireless, Bluetooth, low energy Bluetooth, RFID, hypersonic, Wi-Fi, cellular 3G, 4G, GSM, LiFi, or other method). In some embodiments, the payment token is provisioned to the mobile wallet circuit 216 in advance and is reused for many mobile wallet transactions. In other embodiments, the payment token is dynamically provisioned to the mobile wallet circuit 216. For example, when the user selects the “pay now” button, the mobile wallet circuit 216 may send a request to a mobile wallet computer system (not shown) which, in response, provisions a one-time payment token to the mobile wallet circuit 216.

At step 403, after receiving the payment token, the merchant computer system 104 sends the transaction to an acquirer processor computer system 112 for processing. Next, at step 405, the acquirer processor computer system 112 sends the payment token to the card network computer system 108 for processing a payment. The card network computer system 108 detokenizes the payment token, thereby resulting in the actual card number (PAN). At step 407, the card network computer system 108 sends the PAN to the FI computer system 102. The FI computer 102 then processes the transaction, for example, by approving the transaction based on the account status of the user (e.g., by confirming that the user has not exceed the credit limit of their credit card). The FI computer system 102 may then send an approval to the merchant computing system 106 via the card network computer system 108, the acquirer processor 112 (steps 409-413), and the payment to the merchant is made. Upon receiving the approval message, the point of sale system 140 may generate a receipt for the user. In some embodiments, the receipt may be sent to the mobile device 110 electronically. In other embodiments, the receipt may be printed physically at the point of sale location.

In the preceding example, it is assumed that the user pays the merchant with a pre-existing payment card (i.e., from a payment card account that was in existence prior to the user visiting the merchant). In other situations, the user may pay the merchant with a new payment card. For example, the user may be at a merchant that has an online mechanism for creating a credit application for a merchant-specific payment card (e.g., a store-branded credit card). For example, the customer may use the mobile device 104 to download and install a merchant software application. Using the software application, at the point of sale, the customer may apply for and open a new payment card account (e.g., a new credit card account). The financial institution associated with the merchant-specific payment card may then electronically activate the new payment card and provision the new payment card to the customer (e.g., to a mobile wallet application executed by the customer device 104). The customer may then use the new payment card at the point of sale. At the same time, the physical payment card may be mailed to the customer, and the customer may activate the physical payment card upon receipt in the mail.

The scope of this disclosure should be determined by the claims, their legal equivalents and the fact that it fully encompasses other embodiments which may become apparent to those skilled in the art. All structural, electrical and functional equivalents to the elements of the below-described disclosure that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. A reference to an element in the singular is not intended to mean one and only one, unless explicitly so stated, but rather it should be construed to mean at least one. No claim element herein is to be construed under the provisions of 35 U.S.C. § 112, sixth paragraph, unless the element is expressly recited using the phrase “means for.” Furthermore, no element, component or method step in the present disclosure is intended to be dedicated to the public, regardless of whether the element, component or method step is explicitly recited in the claims.

The embodiments in the present disclosure have been described with reference to drawings. The drawings illustrate certain details of specific embodiments that implement the systems, methods and programs of the present disclosure. However, describing the embodiments with drawings should not be construed as imposing any limitations that may be present in the drawings. The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing its operations. The embodiments of the present disclosure may be implemented using an existing computer processor, or by a special purpose computer processor incorporated for this or another purpose or by a hardwired system.

As used herein, “circuit” may include program logic executable by hardware disposed at a computing system to implement at least some of the functions described herein. Embodiments within the scope of the present invention include program products comprising non-transitory machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media may be any available media that may be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media may comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to carry or store desired program code in the form of machine-executable instructions or data structures and which may be accessed by a general purpose or special purpose computer or other machine with a processor. Thus, any such a connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Embodiments in the present disclosure have been described in the general context of method steps which may be implemented in one embodiment by a program product including machine-executable instructions, such as program code, for example, in the form of program modules executed by machines in networked environments. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Machine-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.

As previously indicated, embodiments in the present disclosure may be practiced in a networked environment using logical connections to one or more remote computers having processors. Those skilled in the art will appreciate that such network computing environments may encompass many types of computers, including personal computers, handheld devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and so on. Embodiments in the disclosure may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

An exemplary system for implementing the overall system or portions of the disclosure might include one or more computers including a processor, a system memory or database, and a system bus that couples various system components including the system memory to the processor. The database or system memory may include read only memory (ROM) and random access memory (RAM). The database may also include a magnetic hard disk drive for reading from and writing to a magnetic hard disk, a magnetic disk drive for reading from or writing to a removable magnetic disk, and an optical disk drive for reading from or writing to a removable optical disk such as a CD ROM or other optical media. The drives and their associated machine-readable media provide nonvolatile storage of machine-executable instructions, data structures, program modules and other data for the computer. User interfaces, as described herein, may include a computer with a monitor, a keyboard, a keypad, a mouse, a joystick or other input devices performing a similar function.

It should be noted that although the diagrams herein may show a specific order and composition of method steps, it is understood that the order of these steps may differ from what is depicted. For example, two or more steps may be performed concurrently or with partial concurrence. Also, some method steps that are performed as discrete steps may be combined, steps being performed as a combined step may be separated into discrete steps, the sequence of certain processes may be reversed or otherwise varied, and the nature or number of discrete processes may be altered or varied. The order or sequence of any element or apparatus may be varied or substituted according to alternative embodiments. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. Such variations will depend on the software and hardware systems chosen and on designer choice. It is understood that all such variations are within the scope of the disclosure. Likewise, software and web implementations of the present invention could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps.

The foregoing description of embodiments has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the subject matter to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the subject matter disclosed herein. The embodiments were chosen and described in order to explain the principals of the disclosed subject matter and its practical application to enable one skilled in the art to utilize the disclosed subject matter in various embodiments and with various modifications as are suited to the particular use contemplated. Other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangement of the embodiments without departing from the scope of the presently disclosed subject matter.

Throughout the specification, numerous advantages of the exemplary embodiments have been identified. It will be understood, of course, that it is possible to employ the teachings herein without necessarily achieving the same advantages. Additionally, although many features have been described in the context of a particular data processor, it will be appreciated that such features could also be implemented in the context of other hardware configurations.

While the exemplary embodiments illustrated in the figures and described above are presently preferred, it should be understood that these embodiments are offered by way of example only. Other embodiments may include, for example, structures with different data mapping or different data. The disclosed subject matter is not limited to a particular embodiment, but extends to various modifications, combinations, and permutations that nevertheless fall within the scope and spirit of the appended claims. 

What is claimed is:
 1. A computing system comprising: an electronic payment token database retrievably storing a plurality of merchant-specific electronic payment tokens and token information associated with each of the plurality of merchant-specific electronic payment tokens, wherein each electronic payment token of the plurality of merchant-specific electronic payment tokens comprises tokenized data corresponding to a payment account and a respective merchant; a network interface circuit enabling the computing system to exchange information over a network; and a token management circuit configured to: display a graphical user interface on a customer device over the network, wherein the graphical user interface includes: a first selectable merchant field configured to trigger, in response to selections therein, at least one of enabling or disabling usability of a first merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from a first payment account to a first merchant, and at least one of enabling or disabling usability of a second merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from the first payment account to a second merchant, and a second selectable merchant field configured to trigger, in response to selections therein, at least one of enabling or disabling usability of a third merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from a second payment account to the first merchant, and at least one of enabling or disabling usability of a fourth merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from the second payment account to the second merchant; display, on the graphical user interface on the customer device, a list of the plurality of merchant-specific electronic payment tokens, such that the first selectable merchant field and the second selectable merchant field are displayed in the list; detect, via the first selectable merchant field displayed in the list on the customer device, a first selection to allow electronic payments from the first payment account to the first merchant; allow, in response to the first selection and via a first update to the electronic payment token database, a first electronic payment from the first payment account to the first merchant submitted with the first merchant-specific electronic payment token for processing; subsequent to the first electronic payment, detect, via the first selectable merchant field displayed in the list on the customer device, a second selection to prevent future electronic payments from the first payment account to the first merchant; disallow, in response to the second selection and via a second update to the electronic payment token database, a second electronic payment from the first payment account to the first merchant submitted with the first merchant-specific electronic payment token for processing; detect, via the second selectable merchant field displayed in the list on the customer device, a third selection to allow future electronic payments from the second payment account to the first merchant; allow, in response to the third selection and via a third update to the electronic payment token database, a third electronic payment from the second payment account to the first merchant submitted with the third merchant-specific electronic payment token for processing; receive, from the customer device, a request to update information of a user of the customer device, different from the plurality of merchant-specific electronic payment tokens, that is stored in a customer database, the request comprising updated information that replaces the information in the customer database; identify, from the customer database and responsive to receiving the request to update the information in the customer database, one or more merchants corresponding to previous payment transactions involving the user; identify one or more confirmed merchants from the one or more merchants based on a comparison of the one or more merchants identified in the previous payment transactions and one or more respective merchants corresponding to one or more merchant-specific electronic payment tokens of the plurality of merchant-specific electronic payment tokens that are enabled; and transmit, responsive to the identification of the one or more confirmed merchants, the updated information to a computing device of each of the one or more confirmed merchants.
 2. The computing system of claim 1, wherein the graphical user interface further includes a merchant deletion field displayed in the list, and wherein the token management circuit is further configured to delete a merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in response to receiving a deletion request from the graphical user interface caused by selection of the merchant deletion field.
 3. The computing system of claim 1, wherein the graphical user interface includes an enable toggle and a disable toggle for each merchant identified in the list of the graphical user interface.
 4. The computing system of claim 1, wherein the first and second merchant-specific electronic payment tokens include tokenized versions of a first primary account number of the first payment account, and wherein the third and fourth merchant-specific tokens include tokenized versions of a second primary account number of the second payment account.
 5. The computing system of claim 1, wherein the list of the graphical user interface includes all merchants having an electronic payment token corresponding to the first payment account or the second payment account, and wherein the list includes a respective selectable merchant field for each merchant corresponding to each payment account.
 6. The computing system of claim 5, wherein the list of the graphical user interface further includes a merchant deletion field for each merchant corresponding to each payment account, and wherein the second update of the electronic payment token database prevents future electronic payments submitted for processing with a first merchant-specific electronic token without deleting the first merchant-specific electronic payment token from the electronic payment token database and without removing the merchant from a list of merchants.
 7. The computing system of claim 1, wherein the token management circuit is further configured to search transaction histories of the customer database to identify the one or more merchants corresponding to the previous payment transactions involving the user.
 8. The computing system of claim 1, wherein the token management circuit is configured to allow the first electronic payment to the first merchant based on a payment token status in the electronic payment token database and disallow the second subsequent electronic payment to the first merchant based on the payment token status.
 9. The computing system of claim 1, wherein the graphical user interface is a second graphical user interface, and wherein the token management circuit is further configured to, before displaying the second graphical user interface: display a first graphical user interface on the customer device over the network, the first graphical user interface comprising a virtual menu button configured to trigger, in response to selection thereof, display of a token management hub; and detect, via the first graphical user interface, selection to display the token management hub, wherein the token management circuit is configured to display the second graphical user interface in response to selection of the virtual menu button.
 10. The computing system of claim 1, wherein the graphical user interface further displays a notification providing notice of a status or condition relating to one of the first and second payment accounts.
 11. A method, comprising: storing, in an electronic payment token database, a plurality of merchant-specific electronic payment tokens and token information associated with each of the plurality of merchant-specific electronic payment tokens, wherein each electronic payment token of the plurality of merchant-specific electronic payment tokens corresponds to a payment account and a respective merchant, and wherein the token information includes payment token statuses which are checked by a financial institution computing system in determining whether to allow or disallow electronic payments involving the plurality of merchant-specific electronic payment tokens; displaying a graphical user interface on a customer device over the network, wherein the graphical user interface includes: a first selectable merchant field configured to trigger, in response to selections therein, at least one of enabling or disabling usability of a first merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from a first payment account to a first merchant, and at least one of enabling or disabling usability of a second merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from the first payment account to a second merchant, and a second selectable merchant field configured to trigger, in response to selections therein, at least one of enabling or disabling usability of a third merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from a second payment account to the first merchant, and at least one of enabling or disabling usability of a fourth merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from the second payment account to the second merchant; displaying, on the graphical user interface on the customer device, a list of the plurality of merchant-specific electronic payment tokens, such that the first selectable merchant field and the second selectable merchant field are displayed in the list; detecting, via the first selectable merchant field displayed in the list on the customer device, a first selection to allow electronic payments from the first payment account to the first merchant; allowing, in response to the first selection and via a first update to the electronic payment token database, a first electronic payment from the first payment account to the first merchant submitted for with the first merchant-specific electronic payment token for processing; subsequent to the first electronic payment, detecting, via the first selectable merchant field displayed in the list on the customer device, a second selection to prevent future electronic payments from the first payment account to the first merchant; disallowing, in response to the second selection and via a second update to the electronic payment token database, a second electronic payment from the first payment account to the first merchant submitted with the first merchant-specific electronic payment token for processing; detecting, via the second selectable merchant field displayed in the list on the customer device, a third selection to allow future electronic payments from the second payment account to the first merchant; allowing, in response to the third selection and via a third update to the electronic payment token database, a third electronic payment from the second payment account to the first merchant submitted with the third merchant-specific electronic payment token for processing; receiving, from the customer device, a request to update information of a user of the customer device, different from the plurality of merchant-specific electronic payment tokens, that is stored in a customer database, the request comprising updated information that replaces the information in the customer database; identifying, from the customer database and responsive to receiving the request to update the information in the customer database, one or more merchants corresponding to previous payment transactions involving the user; identifying one or more confirmed merchants from the one or more merchants based on a comparison of the one or more merchants identified in the previous payment transactions and one or more respective merchants corresponding to one or more merchant-specific electronic payment tokens of the plurality of merchant-specific electronic payment tokens that are enabled; and transmitting, responsive to the identification of the one or more confirmed merchants, the updated information to a computing device of each of the one or more confirmed merchants.
 12. The method of claim 11, wherein the list of the graphical user interface includes a merchant deletion field displayed in the list, and wherein the token management circuit is further configured to delete a merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in response to receiving a deletion request from the graphical user interface caused by selection of the merchant deletion field.
 13. The method of claim 12, wherein the first and second merchant-specific electronic payment tokens include tokenized versions of a first primary account number of the first payment account, and the third and fourth merchant-specific electronic payment tokens include tokenized versions of a second primary account number of the second payment account.
 14. The method of claim 12, wherein the list of the graphical user interface includes all merchants having an electronic payment token corresponding to a particular payment account, and wherein the list includes a respective toggle for each merchant.
 15. The method of claim 14, wherein updating the electronic payment token database such that subsequent electronic payments using the third merchant-specific electronic payment token are disallowed di sables the third merchant-specific electronic payment token without deleting the third merchant-specific electronic payment token and without removing the merchant from a list of merchants.
 16. The method of claim 12, wherein the list of the graphical user interface further comprises a first virtual reprovisioning button corresponding to the first payment account and a second virtual reprovisioning button corresponding to the second payment account, the method further comprising: detecting, via the graphical user interface, selection of the first virtual reprovisioning button; and initiating, by the financial institution computing system, issuance of a new payment card with a new primary account number in response to detecting selection of the first virtual reprovisioning button.
 17. A non-transitory computer readable media having computer-executable instructions embodied therein that, when executed by a processor of a computing system, cause the computing system to perform operations comprising: storing, in an electronic payment token database, a plurality of merchant-specific electronic payment tokens and token information associated with each of the plurality of merchant-specific electronic payment tokens, wherein each token of the plurality of merchant-specific electronic payment tokens corresponds to a payment account and a respective merchant, and wherein the token information for each electronic payment token includes a payment token status which is checked by the computing system in determining whether to allow or disallow electronic payments involving the electronic payment token; displaying, on a customer device over a network, a graphical user interface comprising: a first selectable merchant field configured to trigger, in response to selections therein, at least one of enabling or disabling usability of a first merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from a first payment account to a first merchant, and at least one of enabling or disabling usability of a second merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from the first payment account to a second merchant, and a second selectable merchant field configured to trigger, in response to selections therein, at least one of enabling or disabling usability of a third merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from a second payment account to the first merchant, and at least one of enabling or disabling usability of a fourth merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in making electronic payments from the second payment account to the second merchant; displaying, on the graphical user interface on the customer device, a list of the plurality of merchant-specific electronic payment tokens such that the first selectable merchant field and the second selectable merchant field are displayed in the list; detecting, via the first selectable merchant field displayed in the list on the customer device, a first selection to allow electronic payments from the first payment account to the first merchant; allowing, in response to the first selection and via a first update to the electronic payment token database, a first electronic payment from the first payment account to the first merchant submitted with the first merchant-specific electronic payment token for processing; subsequent to the first electronic payment, detecting, via the first selectable merchant field displayed in the list on the customer device, a second selection to prevent future electronic payments from the first payment account to the first merchant; disallowing, in response to the second selection and via a second update to the electronic payment token database, a second electronic payment from the first payment account to the first merchant submitted with the first merchant-specific electronic payment token for processing; detecting, via the second selectable merchant field displayed in the list on the customer device, a third selection to allow future electronic payments from the second payment account to the first merchant; allowing, in response to the third selection and via a third update to the electronic payment token database, a third electronic payment from the second payment account to the first merchant submitted with the third merchant-specific electronic payment token for processing; receiving, from the customer device, a request to update information of a user of the customer device, different from the plurality of merchant-specific electronic payment tokens, that is stored in a customer database, the request comprising updated information that replaces the information in the customer database; identifying, from the customer database and responsive to receiving the request to update the information in the customer database, one or more merchants corresponding to previous payment transactions involving the user; identifying one or more confirmed merchants from the one or more merchants based on a comparison of the one or more merchants identified in the previous payment transactions and one or more respective merchants corresponding to one or more merchant-specific electronic payment tokens of the plurality of merchant-specific electronic payment tokens that are enabled; and transmitting, responsive to the identification of the one or more confirmed merchants, the updated information to a computing device of each of the one or more confirmed merchants.
 18. The non-transitory computer-readable media of claim 17, wherein the list of the graphical user interface includes a merchant deletion field displayed in the list, and wherein the token management circuit is further configured to delete a merchant-specific electronic payment token of the plurality of merchant-specific electronic payment tokens in response to receiving a deletion request from the graphical user interface caused by selection of the merchant deletion field.
 19. The non-transitory computer-readable media of claim 17, wherein the list of the graphical user interface further comprises a first virtual reprovisioning button corresponding to the first payment account and a second virtual reprovisioning button corresponding to the second payment account, and wherein the computer-executable instructions, when executed by the processor of the computing system, cause the computing system to perform operations further comprising: receiving, from the customer device at the graphical user interface, selection of the first virtual reprovisioning button; and initiating issuance of a new payment card with a new primary account number in response to receiving the third indication.
 20. The non-transitory computer-readable media of claim 17, wherein the graphical user interface is a second graphical user interface, and wherein the computer-executable instructions, when executed by the processor of the computing system, cause the computing system to perform operations further comprising: displaying a first graphical user interface on the customer device, the first graphical user interface comprising a selectable virtual menu button configured to trigger display of a token management hub; and detecting, via the first graphical user interface, selection of the virtual menu button, wherein the computing system displays the second graphical user interface in response to detecting selection of the virtual menu button. 